Nuclear_Rat

Category: rat · Aliases: NuclearRAT, Nuclear RAT 2.1, Backdoor.NuclearRat, Trojan.NuclearRAT, Win32/NuclearRAT · Sample count (EMBER 2018): 0 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: RatSeverity: HIGHStatus: Automated SignaturePlatform: WINDOWS_PEStage: Initial Access, Execution, Command And Control, CollectionFirst seen: 2003Motivation: Espionage🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Nuclear RAT (cataloged across security software as NuclearRAT, Nuclear RAT 2.1, Backdoor.NuclearRat, and Trojan.NuclearRAT) is a classic open-source Remote Access Trojan created in 2003 by the developer 'caesar2k'.

Table of Contents

Overview

Nuclear RAT (cataloged across security software as NuclearRAT, Nuclear RAT 2.1, Backdoor.NuclearRat, and Trojan.NuclearRAT) is a classic open-source Remote Access Trojan created in 2003 by the developer 'caesar2k'. Programmed in C++ and Visual C++, Nuclear RAT gained prominence in early cybercrime circles due to its reverse-connection architecture, allowing it to bypass inbound perimeter NAT firewalls by having the compromised client initiate outbound TCP sessions to the operator's DNS or IP. Features include an interactive remote command shell, full file system manipulation, live desktop streaming, webcam frame capture, audio microphone eavesdropping, process injection, keystroke logging, and early rootkit hooks designed to conceal its process image from the Windows Task Manager.

Known aliases

Threat reports may refer to this family under multiple names:

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Early C++ Reverse Rat Frameworks

Known Derivatives & Downstream Variants: Nuclear Rat 1.0 · Nuclear Rat 2.0 · Nuclear Rat 2.1

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-PIADProcess Injection Analysis & DetectionDetectT1055.002Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-PBAProcess Spawn AnalysisDetectT1059.003Inspect command-line arguments and anomalous parent-child relationships spawning from cmd.exe.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-RVMRegistry Value Modification AnalysisDetectT1112Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings.
D3-SDScreen Capture DetectionDetectT1113Monitor desktop graphics API calls (BitBlt, GetDC) triggered by non-standard background threads.
D3-HACHardware Device Access ControlIsolateT1125Enforce Group Policy hardware access restrictions on integrated webcams and microphones.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

rule MALWARE_WIN_NUCLEAR_RAT_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Nuclear_Rat"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "nuclear_rat" ascii wide nocase
        $s2 = "nuclearrat" ascii wide nocase
        $s3 = "nuclear rat 2.1" ascii wide nocase
        $s4 = "backdoor.nuclearrat" ascii wide nocase
        $s5 = "trojan.nuclearrat" ascii wide nocase
        $s6 = "win32/nuclearrat" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Nuclear_rat (Rat) Execution & Triage
id: 41d679f0-2cd2-5fec-9fb0-dc0c1d6b579e
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Nuclear_rat malware family. Detects unauthorized persistence creation via
  Windows Registry Run keys, scheduled tasks, and privilege escalation indicative
  of RAT installations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/nuclear_rat
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.rat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1055_002
- attack.t1056_001
- attack.t1113
- attack.t1125
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \reg.exe
    - \schtasks.exe
    - \cmd.exe
    - \powershell.exe
    CommandLine|contains:
    - \CurrentVersion\Run
    - /create /tn
    - bypass -enc
    - net user /add
    - net localgroup administrators
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_NUCLEAR_RAT_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Nuclear_Rat tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "nuclear_rat" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Sever outbound network connections immediately to block reverse-connection C2 communication.
  2. Inspect running processes and loaded modules using kernel diagnostic tools to reveal hidden binaries.
  3. Remove persistent startup keys located in HKLM\Software\Microsoft\Windows\CurrentVersion\Run.
  4. Deploy endpoint security software to quarantine dropped executables and clean hooked APIs.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not rely solely on standard Task Manager to verify infection status, as rootkit hooks may conceal the process.
  2. Avoid entering sensitive administrative credentials before performing full system memory verification.

References & External Analysis

Frequently Asked Questions

What is the Nuclear RAT remote access trojan?

Nuclear RAT is an early C++ Remote Access Trojan created in 2003 that popularized reverse-connection outbound C2 communications.

Why was Nuclear RAT considered technically significant?

It established early standards for NAT firewall traversal via reverse callbacks and integrated rootkit process hiding hooks.

What surveillance features did Nuclear RAT provide?

It provided desktop streaming, webcam capture, microphone eavesdropping, keystroke logging, and remote shell access.

Which CVE vulnerabilities have been associated with Nuclear RAT delivery?

Campaigns distributing retro RAT droppers have exploited document and shortcut flaws including CVE-2010-2568 and CVE-2012-0158.

How can systems be defended against Nuclear RAT?

Enforce firewall egress filtering, monitor autostart registry entries, and deploy modern EDR agents capable of detecting unhooked processes.

How do I remove the Nuclear_Rat Rat from Windows?

Manual removal of Nuclear_Rat is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Nuclear_Rat a virus or a Rat?

Nuclear_Rat is classified as a Rat. Unlike traditional viruses that infect files, modern malware like Nuclear_Rat typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Nuclear_Rat infection?

Symptoms of Nuclear_Rat can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Rats

Want to prevent Nuclear_Rat and similar threats from compromising your organization? Read our comprehensive defensive guide: Backdoor & RAT Protection for Businesses.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/nuclear_rat.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.